fix(cli): revert broken merge and stabilize captured process containment - #110
Conversation
f9c11fc to
7d6d024
Compare
|
|
Integration-lane review response Thanks for the automated reports and review feedback. I have triaged this PR against the current
For draft PRs, merge approval is held until the PR is ready and all required checks complete. For ready PRs, required checks are being rerun/monitored; approval follows only after the full rollup is green. No merge bypass is being used. |
marlonsc
left a comment
There was a problem hiding this comment.
Approved for the 0.12.0-dev integration lane. Required checks are green; atomic write metadata stabilization is compatible with the current baseline.
marlonsc
left a comment
There was a problem hiding this comment.
Approved for the integration lane. Required check rollup is green and all reviewer comments have a response.



Reverts broken merge d58c2f2 and applies captured-process-containment runtime gates:
Summary by cubic
Routes
run_rawandrun_bytesthrough the same streamed containment lifecycle as the rest of the CLI, so timed-out captured subprocesses no longer leak. New_runtime_process_output.pyand_runtime_process_timing.pymodules own each child pipe and centralize deadline policy; captured stdout and stderr are now returned separately instead of merged, and capture and durable output are now mutually exclusive. Containment tests verify no owned descendant survives a timeout or deadline.Written for commit 7d6d024. Summary will update on new commits.